fix(consensus-overview): use flat page size to prevent truncation on dimensional data#429
Merged
fix(consensus-overview): use flat page size to prevent truncation on dimensional data#429
Conversation
…dimensional data Reorgs (multiple rows per depth) and block proposal status (multiple rows per status) were truncated at longer time ranges because pageSize assumed 1 row per time bucket. Replace per-range pageSize tuning with a flat 10k constant.
Savid
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/ethereum/consensus/overviewwere truncated at longer time ranges (180d, 1y, etc.) becausepageSizeassumed 1 row per time bucketdepthdimension (multiple rows per day) and block proposal status has astatusdimension (canonical/orphaned/missed) — so the old per-rangepageSize(e.g. 180 for 180d) would only fetch 180 total rows, covering far fewer actual dayspageSizetuning with a flatPAGE_SIZE = 10_000constant for all queries